Skip to content

[hical] Add port version 1.0.1#51110

Draft
Hical61 wants to merge 7 commits intomicrosoft:masterfrom
Hical61:master
Draft

[hical] Add port version 1.0.1#51110
Hical61 wants to merge 7 commits intomicrosoft:masterfrom
Hical61:master

Conversation

@Hical61
Copy link
Copy Markdown

@Hical61 Hical61 commented Apr 12, 2026

Description

Add new port hical version 1.0.1.

hical is a modern C++20/C++26 high-performance web framework built on
Boost.Asio/Beast, featuring PMR memory pools, coroutine-based async I/O,
C++20 Concepts, and a C++26 reflection layer.

New Port Checklist

  • Changes comply with the maintainer guide.
  • The packaged project shows strong association with the chosen port name.
    • The port name follows the 'GitHubOrg-GitHubRepo' form or equivalent Owner-Project form.
  • Optional dependencies of the build are all controlled by the port. A dependency is controlled if it is declared an unconditional dependency in vcpkg.json, or explicitly disabled through patches or build system arguments such as CMAKE_DISABLE_FIND_PACKAGE_Xxx or VCPKG_LOCK_FIND_PACKAGE.
  • The versioning scheme in vcpkg.json matches what upstream says.
  • The license declaration in vcpkg.json matches what upstream says.
  • The installed as the "copyright" file matches what upstream says.
  • The source code of the component installed comes from an authoritative source.
  • The generated "usage text" is brief and accurate. See adding-usage for context.
  • The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
  • Exactly one version is added in each modified versions file.

@Hical61
Copy link
Copy Markdown
Author

Hical61 commented Apr 12, 2026

@microsoft-github-policy-service agree

Copy link
Copy Markdown
Member

@BillyONeal BillyONeal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please complete the actual new port checklist rather than making up some other checklist:

  • Changes comply with the maintainer guide.
  • The packaged project shows strong association with the chosen port name. Check this box if at least one of the following criteria is met:
    • The project is in Repology: https://repology.org//versions
    • The project is amongst the first web search results for "" or " C++". Include a screenshot of the search engine results in the PR.
    • The port name follows the 'GitHubOrg-GitHubRepo' form or equivalent Owner-Project form.
  • Optional dependencies of the build are all controlled by the port. A dependency is controlled if it is declared an unconditional dependency in vcpkg.json, or explicitly disabled through patches or build system arguments such as CMAKE_DISABLE_FIND_PACKAGE_Xxx or VCPKG_LOCK_FIND_PACKAGE
  • The versioning scheme in vcpkg.json matches what upstream says.
  • The license declaration in vcpkg.json matches what upstream says.
  • The installed as the "copyright" file matches what upstream says.
  • The source code of the component installed comes from an authoritative source.
  • The generated "usage text" is brief and accurate. See adding-usage for context. Don't add a usage file if the automatically generated usage is correct.
  • The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
  • Exactly one version is added in each modified versions file.

@BillyONeal
Copy link
Copy Markdown
Member

See also Hical61#1

@BillyONeal BillyONeal marked this pull request as draft April 15, 2026 03:16
@Hical61 Hical61 marked this pull request as ready for review April 15, 2026 04:21
@Hical61
Copy link
Copy Markdown
Author

Hical61 commented Apr 15, 2026

@BillyONeal Checklist updated and all previous issues fixed. Ready for review.

Copy link
Copy Markdown
Member

@BillyONeal BillyONeal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[x] The port name follows the 'GitHubOrg-GitHubRepo' form or equivalent Owner-Project form.

You checked this but it isn't actually true, that form would be hical61-hical. I think things are close enough that we might be able to take that difference under normal conditions, but unfortunately the name "hical" appears to have strong associations with other entities, for example https://www.hical.com/ who make solenoids motors and stuff, https://hical.ca/ who make guns, or the Chinese space agency Hainan International Commercial Aerospace Launch Co., Ltd. ( https://en.wikipedia.org/wiki/HICAL ). And if any of these ever decided to publish a C++ library with us that name being already used would be problematic.

Would you accept naming the port hical61-hical? Note that this is only about what the vcpkg port is named, this isn't an ask to rename your actual project or anything it actually installs.

Comment thread ports/hical/usage
@@ -0,0 +1,4 @@
hical provides CMake integration targets:
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This usage file is substantially identical to the automatically generated one so we should remove it.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed, I'll remove the usage file.

@BillyONeal BillyONeal marked this pull request as draft April 15, 2026 23:54
@Hical61
Copy link
Copy Markdown
Author

Hical61 commented Apr 16, 2026

[x] 端口名称遵循“GitHubOrg-GitHubRepo”格式或等效的 Owner-Project 格式。

你检查过了,但实际上并非如此,那种形式应该是…… hical61-hical。我认为两者之间的差距足够小,在正常情况下我们可以忽略这一点,但不幸的是,“hical”这个名字似乎与其他实体有着很强的关联,例如生产电磁阀、电机等产品的https://www.hical.com/ ,生产枪支的https://hical.ca/,以及中国航天机构海南国际商业航天发射有限公司(https://en.wikipedia.org/wiki/HICAL)。如果这些公司决定与我们合作发布C++库,那么这个名字已经被使用就会造成问题。

您是否接受为端口命名hical61-hical?请注意,这仅涉及 v​​cpkg 端口的名称,并非要求您重命名实际项目或其安装的任何内容。

@BillyONeal I understand the naming concern. Would hical-cpp be acceptable?
It's concise and clearly identifies this as a C++ library, avoiding confusion
with the other entities you mentioned.

@Hical61 Hical61 marked this pull request as ready for review April 16, 2026 01:23
@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines:
Successfully started running 1 pipeline(s).

@Hical61 Hical61 marked this pull request as draft April 16, 2026 01:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants